<div id="overlord">
	<div id="header">
	<h1>autoASSET</h1>
	</div>
	<div id="body">
		<h2>Managing your assets, wherever they be</h2>
		<p>And they can be pretty much anywhere!</p>
		<hr />
		<h2>Basic Concept:</h2>
		<h3>AUTOHTML_ASSET_MANAGER</h3>
		<p>Asset sources are kept by a Manager (AUTOHTML_ASSET_MANAGER), which in addition to collecting them provides you an interface with which to access all of them seamlessly.</p>
		<h3></h3>
		<p>Asset sources are basically key-value stores, with the key being the identifier of the asset. This key will most likely resemble a filepath (e.g., '/subject/my_view.html') that mirrors your website url structure. Value is the content of the asset.</p>
		<h3>AUTOHTML_ASSET_FILESYSTEM</h3>
		<p>You may use whatever naming scheme you prefer for the key, but the main reason for doing so is to make it easy to keep assets in flat files using the Filesystem store (AUTOHTML_ASSET_FILESYSTEM). When instantiated, you pass the store the root directory of your assets, and it will look for assets in the subdirectories. (Note that there is [currently] no protection keeping the caller from making their way out to other files).</p>
		<h3>AUTOHTML_ASSET_MEMORY</h3>
		<p>Second to be mentioned, but the most important and basic source is the Memory store (AUTOHTML_ASSET_MEMORY). This store is important to capture dynamic code </p>
	</div>
</div>
